Stop paying for cloud execution limits. By self-hosting n8n on your own infrastructure, you own your data, eliminate task-based costs, and unlock enterprise-grade automation power.
1The Docker Standard
Docker is a containerization platform that allows you to package n8n and all its dependencies into a single 'container'. This ensures that n8n runs exactly the same on your local laptop as it does on a professional VPS in the cloud.
By using Docker Compose, you can define your entire infrastructure—including the n8n engine, the database, and the reverse proxy—as a simple YAML file. This makes your automation stack portable, version-controlled, and easily reproducible. Instead of clicking through confusing server menus, your infrastructure becomes code.
# docker-compose.yml
version: '3.8'
services:
n8n:
image: n8nio/n8n:latest
restart: always
ports:
- "5678:5678"
environment:
- N8N_HOST=n8n.yourdomain.com
- WEBHOOK_URL=https://n8n.yourdomain.com/2Persistence is Power
Containers are 'ephemeral' by nature—meaning if you stop them or they crash, any data stored inside them is lost. To build a production-ready system, you must use Volumes.
Volumes act as a secure bridge between the container and your host server's physical hard drive. By mounting a volume to /home/node/.n8n, you ensure that your workflows, credentials, and execution history survive container restarts, system updates, and server migrations. Without a volume, your first server reboot will delete your entire automation business.
# Adding persistent storage
services:
n8n:
# ... previous config
volumes:
- n8n_data:/home/node/.n8n
volumes:
n8n_data:
external: false3Vault Security
When you self-host, you are responsible for the security of your API keys. n8n encrypts all credentials in its database, but it requires a master Encryption Key to do so.
You must explicitly set this key in your Docker environment variables. If you lose this key, you will permanently lose access to all connected accounts (OpenAI, Stripe, Salesforce, etc.). Additionally, running n8n behind a reverse proxy (like Traefik or Nginx) ensures all traffic is forced over HTTPS, protecting webhook payloads from being intercepted on the public web.
# Environment Security
services:
n8n:
# ... previous config
environment:
# The master key for the vault
- N8N_ENCRYPTION_KEY=super_secret_string_123!
# Basic Auth for the dashboard
- N8N_BASIC_AUTH_ACTIVE=true
- N8N_BASIC_AUTH_USER=admin
- N8N_BASIC_AUTH_PASSWORD=password_here4Step-by-Step Breakdown
Automation shouldn't come with a monthly invoice for every workflow execution. In this lesson, we're taking full ownership of our infrastructure by self-hosting n8n instead of paying for a metered SaaS plan.
Docker packages n8n and all its dependencies into a single portable container. This docker-compose.yml file defines the n8n service, mapping port 5678 so we can reach the dashboard from our browser.
To keep our workflows safe across restarts, we mount a persistent volume at /home/node/.n8n. Without this, every container restart would wipe our workflows, credentials, and execution history clean.
Checkpoint: What happens to your n8n workflows if you delete the container WITHOUT having a mounted Volume?
- →They are automatically saved to the cloud
- →They are permanently deleted because the container's storage is temporary
Self-hosting means we're responsible for security too. Setting N8N_ENCRYPTION_KEY protects every stored credential, while TZ keeps our scheduled workflows firing at the correct local time.
With our configuration complete, docker-compose up -d spins up the container in detached mode, running quietly in the background while we get back to building automations.
Checkpoint: What does the '-d' flag do when running 'docker-compose up -d'?
- →Debug mode: shows every error
- →Detached mode: runs the container in the background
For serious production workloads, swap SQLite for PostgreSQL. A dedicated database handles concurrent workflow executions far more reliably than a single embedded file.
Pro-tip: you've officially built a sovereign automation engine — no execution caps, no per-task billing, and complete control over your own data and infrastructure.
Checkpoint: True or False: Docker Compose allows you to define multiple services (like n8n + Postgres) in a single file.
- →True
- →False
Installation complete! Your n8n engine is online and ready to receive webhooks, run schedules, and execute workflows around the clock.
Next, we'll step into the n8n interface itself and explore how Nodes and Workflows connect together to build real automations.
Verify a Real Environment Config. Finish checking that every required environment variable is set before n8n starts.
Level Up 🚀
Advanced cheat sheets, SEO tricks, and interview prep for this topic.
Browser Support
Fully supported.
Fully supported.
Fully supported.
Fully supported.
Accessibility (A11y)
1Document Self-Hosted Setup Steps in Accessible Plain Text, Not Just Terminal Screenshots
Installation guides that rely on screenshots of terminal output exclude screen reader users entirely — always pair terminal commands and their expected output with plain text so the setup steps remain fully readable by assistive technology.
<pre aria-label="Terminal command">docker-compose up -d</pre>SEO Implications
- 1
Self-Hosting Cost Comparisons Are a High-Intent Search Topic
Developers evaluating n8n specifically search for 'self-hosted vs n8n cloud cost' and similar comparisons before committing — covering the execution-limit and pricing angle explicitly, not just the installation steps, captures that decision-stage search traffic.
Best Practices
Always Mount a Volume Before Running Any Production Workflow
Treat the volumes: block as non-optional from the very first docker-compose up — retrofitting persistence after workflows already exist risks losing everything if the container is restarted before you add it.
Store the N8N_ENCRYPTION_KEY Outside the Repository, With a Backup
Losing this key permanently locks you out of every stored credential. Keep it in a secrets manager or password vault, not just the .env file on the server, and back it up separately from the server itself.
Frequent Bugs
Running docker-compose up without a mounted volume, then losing all workflows, credentials, and execution history on the next container restart or image update.
Always define a named volume mounted to /home/node/.n8n before running any real workflow. Verify persistence by restarting the container and confirming workflows still exist before treating the instance as production-ready.
Real-World Examples
Migrating from n8n Cloud to Self-Hosted at Scale
Teams that outgrow n8n Cloud's execution-based pricing typically migrate to a self-hosted Docker Compose stack once monthly task volume passes the point where a $5-20/month VPS becomes cheaper than metered cloud execution — often a 10x or greater cost reduction at high volume.
docker-compose up -d
docker exec -it n8n_server n8n export:workflow --all --output=/backup/